Facilitating multi-party conferences, including allocating resources needed for conference while establishing connections with participants

ABSTRACT

A system includes a network interface for sending and receiving one or more of video data and audio data between two or more endpoints. One or more of a video data source and an audio data source located at more than one endpoint and a control unit for controlling one or more of the video data and the audio data between endpoints. The control unit is operable to execute instructions to specify more than one participant in a conference, wherein at least one participant is remotely located and invoke the conference upon receiving one or more requests to connect to the conference by one or more participants. The control unit is further operable to allocate resources upon the conference being invoked and connect participants to the conference.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Provisional Application Ser.No. 61/673,044, filed Jul. 18, 2012, which is incorporated by referencein its entirety herein.

BACKGROUND

The present disclosure relates generally to videoconferencing systems,and more particularly, to facilitating multi-party conferences,including dynamically allocating the resources needed for theconference, while establishing connections with participants.

Audio and/or video conferencing technology has developed to the pointthat it has become, in many cases, a useful substitute for conductinggroup meetings in a variety of environments. Audio and/or videoconferencing entails the exchange of audio, video, and other informationbetween at least two participants that are generally remotely located toone another. An endpoint is provided at each participant location toenable the participants to see or hear each other, or both. The endpointmay include a microphone for capturing audio signals from localparticipants and a speaker for converting audio signals received fromthe remote participants into sound. The endpoint may optionally includea camera for capturing video of local participants and a display devicefor displaying video of remote participants. The endpoint may alsoinclude display devices for displaying digital content. Where more thantwo endpoints participate in a conferencing session, a multipointcontrol unit (MCU) may be used to control the conference. The MCU mayreceive audio, video, and data from one or more endpoints, and thentransmit the audio, video, and data to the appropriate endpoints, via anetwork.

Historically, these multi-party conferences, whether audio or video, orboth, have taken one of two forms: scheduled or ad hoc. Typically whenscheduling a conference, a start time and an end time are provided. Thenumber of conference participants is often provided, and optionally, theidentities of the participants may be provided. Participants may beprovided with contact information, such as a telephone number or webaddress (URL), so that they may contact and join the conference.Depending upon the subject matter of the conference, participants may begiven and/or need to provide appropriate credentials and passcode toauthenticate their identity to gain access to the conference.

When the conference is scheduled, it may be determined if participantsare to contact the conference, known in the art as “dial-in,” or awaitto be contacted by an organizer, or organizers, of the conference knownas “dial-out.” Also resources required to effectuate the conference areoften reserved at the time the conference is scheduled. These resourcesmay include MCUs, conference bridges, dial-out telecommunication lines,and other known resources. Additionally, if the scheduled conference isgoing to be a recurring conference, recurrence information can beprovided at the time the conference is scheduled.

As compared to scheduled conferences, ad hoc conferences, known in theart as “reservationless” conferences, may occur at any time. Inreservationless conferences, the number of conference participants andtheir identities is typically not provided and whether the participantis a dial-in or dial-out participant, may be specified for eachparticipant. However, participants in reservationless conferences aretypically provided with persistent contact information, such as atelephone number or web address (URL), so that they may contact and jointhe conference at any given time. Depending upon the subject matter ofthe conference, participants may be given and/or need to provideappropriate credentials and passcode to authenticate their identity togain access to the conference.

Contrary to scheduled conferences, the resources required to effectuatea reservationless conference are not reserved, since the conference isnot scheduled. Thus, some participants may not be able to join thereservationless conference, since available resources may be exhausted.Optionally, it is sometimes possible to allocate resources as individualparticipants connect to the reservationless conference.

Frequently, it would be convenient to have a dial-out conference on ashort notice. Neither type of traditional conference handles thissituation well. Ad hoc conferences do not support automatic dial-out,although some may support a user portal allowing a manual dial-out. Sucha portal is useful, provided that the conference initiator and/orchairperson has access to such a portal when they need to have theconference. Often, this is not the case. Alternatively, scheduledconferences do provide automatic dial-out, but they do not permitefficient unscheduled use. Thus, what is needed is a new conferencetype.

SUMMARY

In one general embodiment, a method comprises specifying more than oneparticipant in a conference, where at least one participant is locatedremotely. The method continues with invoking the conference uponconnecting one or more participants to the conference, and allocatingresources upon the conference being invoked to connect participants tothe conference.

In another general embodiment, a system includes a network interface forsending and receiving one or more of video data and audio data betweentwo or more endpoints, one or more of a video data source and an audiodata source located at more than one endpoint, and a control unit. Thecontrol unit controls one or more of the video data and the audio databetween endpoints. The control unit is operable to execute instructionsto specify more than one participant in a conference, wherein at leastone participant is remotely located and invoke the conference uponreceiving one or more requests to connect to the conference by one ormore participants. The control unit is further operable to allocateresources upon the conference being invoked and connect participants tothe conference.

In further general embodiment, a method that comprises specifying morethan one participant in a conference, where at least one participant islocated remotely. The method continues with designating at least oneparticipant as chairperson, invoking the conference upon receiving arequest to connect to the conference by the chairperson, and allocatingresources upon the conference being invoked to connect participants tothe conference.

In another general embodiment, a non-transitory computer-readable mediumcomprises instructions to cause one or more processors to specify morethan one participant in a conference where at least one participant islocated remotely and designate at least one participant as chairperson,receive a request to connect to the conference by more than oneparticipant, and determine if the chairperson has requested to connectto the conference. The computer-readable further medium comprisesinstructions to invoke the conference upon receiving the request toconnect to the conference from the chairperson, allocate resources uponthe conference being invoked, and request participants to connect to theconference.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a simplified block diagram of an embodiment of asystem for facilitating multi-party conferences, including allocatingthe resources needed for the conference, while establishing connectionswith participants;

FIG. 2 illustrates an embodiment of an exemplary user interface;

FIG. 3 illustrates another embodiment of an exemplary user interface;

FIG. 4 is a flowchart showing an exemplary method for facilitatingmulti-party conferences; and

FIG. 5 is a flowchart showing an alternative exemplary method forfacilitating multi-party conferences.

DETAILED DESCRIPTION

The following description is made for the purpose of generalillustration and is not meant to limit the inventive concepts claimedherein. Further, particular features described herein can be used incombination with other described features in each of the variouspossible combinations and permutations.

As illustrated in FIG. 1, there is shown generally at 100, an embodimentof a system that facilitates multi-party conferences and dynamicallyallocates the resources needed for the conference, while establishingconnections with participants. In a general embodiment, the system 100includes more than one endpoint 102, 104, 106, and may include aplurality of endpoints. The endpoints 102-106 may communicate over oneor more networks 110 (only one is shown for ease of discussion only). Amultipoint control unit (MCU) 112 may be provided for controllingcommunications between the endpoints 102-106 over the network 110. Insome embodiments, there may be more than one MCU 112 in the system 100.For example, an MCU 112 may be embodied in one or more endpoints102-106.

In the embodiments, the network 110 may take any form including, but notlimited to, a local area network (LAN), a wireless network, or a widearea network (WAN) such as the Internet, peer-to-peer network, etc. Theendpoints 102-106 may be connected to the network 110 either wired 116or wirelessly 114. Additionally, the network 110 may comprise both LANand WAN networks, where the WAN provides connectivity between remotelylocated LAN networks 110. Network communication between the endpoints102-106 may be based on known communication protocols and compressionstandards.

An exemplary endpoint of the system 100 is shown at 102 in FIG. 1. It isto be understood that the exemplary endpoint 102 may comprise anyendpoint 102-106 within the system 100, and may comprise more than oneendpoint 102-106. An endpoint 102-106 may comprise any suitable devicethat facilitates communication between remote parties. Exemplaryendpoints 102-106 may include, but are not limited to, conference phonesthat facilitate audio communication between remotely locatedparticipants; videoconference endpoints that facilitate simultaneoustwo-way video and audio transmissions between remotely locatedparticipants; a desktop computer configured with at least a speaker anda microphone and capable of audio communications; and portable computingdevices. These portable computing devices may include laptop computers118, smartphones 120 and other mobile telephones, tablet computers andother portable computing devices (not shown), any of which are at leastcapable of telecommunication, and optionally, additionally capable ofvideo data communications.

In the embodiments, the exemplary endpoint 102 may include a centralprocessing unit (CPU) 122, such as a microprocessor, and a number ofother components interconnected via a system bus 124. The CPU 122 iscapable of operating and running an operating system. In someembodiments, the CPU 122 may run a graphical interface operating system,such as Windows®, by Microsoft Corporation, of Redmond, Wash. In someembodiments, the endpoint 102 may include a Random Access Memory (RAM)126, an I/O adapter 128, and a user interface adapter 130. The I/Oadapter 128 may be provided for connecting peripheral devices, such as adisk storage unit 132 to the bus 124. The user interface adapter 130 maybe provided for connecting user interface devices such as a keyboard134, mouse 136, camera 138, speaker 140, and microphone 142, to the bus124. Optionally, the camera 138 may comprise a pan-tilt-zoom (PZT)camera, with the orientation, positioning and repositioning, andsettings thereof controlled by the processor 122 and/or user via theuser interface 130.

In optional embodiments, for example if an endpoint 102-106 comprises aportable computing device such as a laptop computer 118, smartphone 120,tablet computer or other portable computing device, the endpoint 102-106may include a Global Positioning System (GPS) device 142. The GPS device142 may be enabled to determine the location of the endpoint 102-106,and thus the participant.

The endpoint 102 may additionally include visual means, such as one ormore display monitors 144 coupled to the bus 124. The monitor 144 mayprovide video data, status indications, and other data to a user. Theprocessor 122 receives data from the user, and optionally the MCU 112,and processes the data for controlling the endpoint 102. In someembodiments, a screen 146 of the monitor 104, or a display screen 148 ofa laptop 118 or smartphone 120, may comprise a touchscreen. A user maymove a pointer 150 (shown in FIG. 2) about the screen 146, 148 usingtheir fingers as known to control elements displayed on the screen 146,148.

An exemplary graphical user interface, for establishing and facilitatingmulti-party conferences, and allocating the resources needed for theconference, while establishing connections with participants isillustrated in FIG. 2 and FIG. 3. A “Create Conference” window is showngenerally at 200 in FIG. 2. In some embodiments, the Create Conferencewindow 200 may comprise a two dimensional graphical user interfacewindow that is arranged on a desktop of a graphical interface operatingsystem, such as Windows®. The Create Conference window 200 may be openedby a mouse-click action on an icon representing the Create Conferencewindow 200 on a desktop of a graphical interface operating system (bothnot shown), as known in the art. The Create Conference window 200 may bedisplayed on one or more endpoints 102-106 and may be opened, closed,sized, moved, hidden, and restored, as is known in the art. The createconference window 200, may include a number of graphical objects forestablishing, facilitating, and terminating multi-party conferences.These graphical objects may include, but are not limited to, a menu bar202, one or more toolbars 204 that may be located in or near the menubar 202, one or more menus 206 that may comprise a pull-down ordrop-down menu, and other graphical user interface elements. Some ofthese graphical user interface elements may include “option” buttons,referred to in the art as “radio” buttons, shown generally at 208,control tabs 210, and other graphical user interface elements, all ofwhich may be located in a working area, shown generally at 212.

The elements of the Create Conference window 200 may be controlled,invoked, activated, or otherwise controlled by means of the pointer 150.The pointer 150 may be controlled by a pointer device, the mouse 136.Optionally, if the monitor 104 is configured with a touchscreen 146,148, the user can move the pointer 150 and select the radio buttons 208,control tabs 210, and other elements of the Create Conference window 200via the touchscreen 146, 148.

In the embodiment shown in FIG. 2, the Create Conference window 200includes a “Create Conference” menu bar 202, an “Add Participant”drop-down menu 206, a “See All Participants” tab 210P, a “CreateConference” tab 210C, and “Cancel” tab 210X. Radio buttons 208 in theembodiment include “Authentication” buttons 208A, “Chairperson” buttons208C, and “Add Participant” buttons 208P. A user 216, or other entity,which establishes a conference is referred to in the art as “host.”Hereinafter, “host” and “user” may be used interchangeably to refer toan individual, group, business entity, or any other entity whichinitiated establishing a conference. Additionally, any endpoint 102-106where the host or user 216 is located is referred to herein as a “hostendpoint”. Thus in the embodiments shown, endpoint 102 will comprise thehost endpoint as discussed hereinafter. Further, as referred tohereinafter, “participant” may be used interchangeably with “endpoint.”Typically one or more participants 218 may be located at and/oroperating any given endpoint 102-106. Thus a participant 218 listed inthe drop-down menu 206 may comprise an individual, more than oneindividual, or group of individuals, or any other entity which arelocated at and/or operate any one endpoint 102-106, and which do notestablish a conference.

The radio buttons 208 allow the host 216 to select participants 218,shown in FIG. 1, and then designate a chairperson from the selectedparticipants 218. The radio buttons 208 also allow the host 216, orsystem 100, to determine other parameters for the selected participants218. For example, the host 216, or system 100, may determine how theselected participants 218 are going to connect to the conference usingdial-in or dial-out radio buttons 208P, and if authentication isrequired, by selecting the appropriate authentication radio button 208A.Referring still to FIG. 2, the host 216 may select a single participant218, more than one participant 218, or all participants 218 from thedrop-down menu 206. The Create Conference window 200 additionally allowsthe user 216 to view all participants 218 of the conference, as well ascancel 210X. The cancel button 210X may be used to terminate cancelationof the creation of a conference, terminate an ongoing conference, orterminate a particular action.

The host 216 may open the Create Conference window 200 and select thecreate conference tab 210C to commence establishing a conference. Thehost 216 then opens the Add Participant drop-down menu 206, and selectsone or more participants 218 from the menu 206. A number of parametersmay be used when establishing the conference. For example, the system100 may use location data, presence data, and other information,provided by the GPS device 142, to locate a potential participant 218.The location data and presence data may be used to determine which MCU112, when the system 100 includes more than one MCU 112, that thepotential participant 218 may connect to, for connecting to theconference.

Location data and presence data may be used together with profileinformation about the potential participant 218 to determine how toconnect the participant 218 to the conference, such as via a dial-out ordial-in connection. For example, if the participant 218, and thusendpoint 104-106 is located in an office building, or similar location,a dial-out connection to the endpoint 104-106 may be preferred.Alternatively, if the participant 218 is traveling, or located whereconferencing capabilities, such as audio conferencing and/or suitablevideoconferencing capabilities are not available, they may connect tothe conference via a dial-in connection, where the participant 218connects to the conference with a mobile device such as the laptop 118or smartphone 120, or other mobile device. Depending upon the locationof the participant 218, as well as the capabilities of the laptop 118 orsmartphone 120, the participant 218 may participate in the conferencevia audio, video, or both.

If the participant 218 is connecting to the host endpoint 102 to via adial-in connection, the participant 218 may connect connecting to thehost endpoint 102 using one or more networks 110. For example, if theparticipant 218 connect to the host endpoint 102 via a network 110, suchas the Internet, via a network interface 152. They may connect to thenetwork 110 either wirelessly 114 or wired connection 116.Alternatively, if the dial-out option is selected, remotely locatedparticipants 218 are contacted by the host 216 using one or morenetworks 110, as discussed.

Upon connecting the selected participants 218 to the host endpoint 102,the participants 218 may be requested to authenticate their identity tothe host 216. For example, the host 216 may select the AuthenticationYES radio button 208A, and require that participants 218 authenticatetheir identity. One or more methods may be used by selected participants218 or the host 216 to authenticate participants 218. Upon connecting tothe host endpoint 102 a participant 218 may authenticate their identityby entering one or more passcodes. The passcodes may be used be used incombination with location data and presence data to authenticate theidentity of an individual, or individuals, as well as endpoint 104-106.Optionally, a biometric scanner 154 may be used in combination with anindividual's passcode to authenticate the identity of an individual.

It may be determined at any time whether the conference will have achairperson. For example, upon authenticating the participants 218selected for the conference, it may then be determined if the conferencewith have a chairperson. The Chairperson radio buttons 208C may beactuated, where selecting the “YES” button indicates that the conferencewill have a chairperson and selecting the “NO” button indicates that theconference will not have a chairperson. Optionally, the Chairpersonradio buttons 208C may be actuated as participants 218 are selected forthe conference, for designating a participant 218 as chairperson uponselecting the participant 218. In some embodiments, a first participant218 that connects to the conference may be designated as chairperson. Inanother embodiment, the chairperson may be selected arbitrarily fromparticipants 218 connected to the conference. The conference maycommence upon the chairperson being connect to the conference andauthenticating.

As illustrated in FIG. 3, the system 100 additionally includes a“Participant Menu” window shown generally at 300. In some embodiments,the Participant Menu window 300 may comprise a two dimensional graphicaluser interface window, that is arranged on a desktop of a graphicalinterface operating system, such as Windows®, as discussed. TheParticipant Menu window 300 may be used to identify the participants 218in a conference and provide other information. The Participant Menuwindow 300 may be displayed on one or more endpoints 102-106 and mayinclude a number of exemplary graphical objects that may include, butare not limited to, a menu bar 302, one or more toolbars 304 that may belocated in or near the menu bar 302, a number of lists 306, and radiobuttons, shown generally at 308, control tabs 310, and other graphicaluser interface elements, all of which may be located in a working area,shown generally at 312.

In some embodiments, the Participant Menu window 300 may displayinformation such as a “Chair” list 306C, that indicates whether theparticipant 218 is designated as a chairperson. The Participant Menuwindow 300 may also include a “Dial” list 306D, that indicates whetherthe participant 218 is a dial-in or dial-out participant 218. Inoptional embodiments, the Participant Menu window 300 may also include“Delete” radio buttons 308D, that allow the host 216 to remove one ormore listed participants 218 from the conference.

An exemplary embodiment of a method for facilitating multi-partyconferences and dynamically allocates the resources needed for theconference, while establishing connections with participants is showngenerally at 400 in FIG. 4. As an option, the method 400 may be carriedout in the context of the architecture and environment the Figures, andparticularly to FIGS. 1-3 of the Figures. However, the method 400 may becarried out in any desired environment.

The method 400 commences in operation 402. In operation 404 it isdetermined to create a conference. In some embodiments, the CreateConference window 200 may be opened to commence creation of theconference, using the methods discussed. Once the Create Conferencewindow 200 is opened, the conference may be created using one or morediscussed methods. In one embodiment, the host 216 selects one or moreparticipants 218 listed in the drop-down menu 206. As an option, thehost 216 may use the radio buttons 208 to select whether authenticationis required using the authentication radio button 208A, and fordesignating one or more participants 218 as chairperson, using theChairperson radio buttons 208C. In some embodiments, the host 216 maydetermine how the selected participants 218 are going to connect to theconference using the dial-in or dial-out radio buttons 208P. In optionalembodiments, the system 100, may determine how the selected participants218 are going to connect to the conference. For example, the system 100may use location data, presence data, and other information, provided bythe GPS device 142, to locate the participant 218 and determine how toconnect the participant 218 to the conference, such as via dial-out ordial-in connection.

In operation 406, in some embodiments, at any time after the conferenceis created selected participants 218, including the chairperson, maycontact the conference. The system 100 receives these dial-ins anddetermines whether one or more participants 218 who've contacted theconference is designated as a chairperson. In operation 408, if at leastone participant 218 designated as a chairperson has not contacted theconference, the conference is not invoked, and the one or moreparticipants 218 is placed in a “delay-connection” state operation 410.The method 400 then returns to operation 406. The delay-connectionstate, of operation 410, is commonly referred to as a “hold,” where aconnection between the participant 218 and system 100 is not terminated,and the conference is not yet invoked. The participant 218 may be placedon hold until at least one participant 218 designated as a chairpersonjoins the conference.

In operation 408, if at least one participant 218 designated as achairperson has contacted the conference, the method 400 continues tooperation 412. In operation 412, in some embodiments, upon at least oneparticipant 218 designated as a chairperson joining the conference, thesystem 100 may contact participants 218 for the purpose of connectingparticipants 218 to the conference. Where a participant 218 isdesignated as dial-out participant, the participant 218 is connected tothe conference upon establishing a connection between the participant218 and the conference.

Also in operation 412, in the embodiments, upon at least one participant218 designated as a chairperson joining the conference, any on-holddial-in participant 218 are connected to the conference. The method 400then continues to operation 414, where resources are allocated asrequired by the system 100 to connect the participants 218 to theconference. Required conference resources may include, but are notlimited to, one or more MCUs 112, one or more network interfaces 152, orbridges, to connect to one or more networks 110, telecommunicationresources, and other resources common to conferencing. Thus, onlyresources required for the conference are allocated by the system 100,as opposed to scheduled conferences, where resources are allocated atthe time the conference is scheduled, or ad hoc conferences, whereresources are never allocated or are allocated as individualparticipants connect to the conference. In optional embodiments, thesystem 100 may allocate only resources to establish a connection withdial-out participants 218.

The method 400 then continues to operation 416 where the conference isbegun. As the conference is on-going, other selected participants 218that are designated as dial-in participants, may be requested to connectto the conference via any one of several different methods. In theembodiments, participants 218 that are designated as dial-inparticipants may be contacted by the system 100 telephonically, viaelectronic mail (e-mail), Short Message Service (SMS) messaging,commonly referred to as text messaging, or via social media. The system100 may send messages to participants 218 that may notify the user todial-in to the conference. Alternatively, the system 100 may notifyparticipants 218 that an attempt to establish a dial-out connection withthem was unsuccessful. If an attempt to establish a dial-out connectionwith them was unsuccessful, the notification may also provide dial-ininformation so the participant 218 may join the conference. Optionally,messages sent to participants 218 may include required authenticationinformation, and other information. The method 400 terminates atoperation 420.

An alternative embodiment of a method for facilitating multi-partyconferences and dynamically allocates the resources needed for theconference, while establishing connections with participants, is showngenerally at 500 in FIG. 5. As an option, the method 500 may be carriedout in the context of the architecture and environment the Figures, andparticularly to FIGS. 1-3 of the Figures. However, the method 500 may becarried out in any desired environment.

The method 500 commences in operation 502. In operation 504 it isdetermined to create a conference. In some embodiments, the CreateConference window 200 may be opened to commence creation of theconference, using the methods previously discussed. Once the CreateConference window 200 is opened, the conference may be created using oneor more discussed methods. In one embodiment, the host 216 selects oneor more participants 218 listed in the drop-down menu 206. As an option,the host 216 may use the radio buttons 208 to select whetherauthentication is required using the authentication radio button 208A,and for designating one or more participants 218 as chairperson, usingthe Chairperson radio buttons 208C. In some embodiments, the host 216may determine how the selected participants 218 are going to connect tothe conference using the dial-in or dial-out radio buttons 208P. Inoptional embodiments, the system 100, may determine how the selectedparticipants 218 are going to connect to the conference. For example,the system 100 may use location data, presence data, and otherinformation, provided by the GPS device 142, to locate the participant218 and determine how to connect the participant 218 to the conference,such as via dial-out or dial-in connection.

In operation 506, in some embodiments, at any time after the conferenceis created selected participants 218 may contact the conference andrequest to connect to the conference. In some embodiments, the system100 receives these dial-ins and determines a first participant 218 whichcontacted the conference in operation 508. The first participant 218that contacted the conference may be designated as chairperson, shown inoperation 508. The method 500 then continues to operation 510 whereresources required to connect the participants 218 to the conference areallocated by the system 100. The conference is begun in operation 512.

As the conference is on-going, other selected participants 218 may becontacted by the system 100 and requested to connect to the conference,in operation 514. These participants 218 may be requested to connect tothe conference via one or more of the several different methodsdiscussed. The method 500 terminates at operation 516.

As will be appreciated by one skilled in the art, aspects of thedisclosure may be embodied as a system, method or non-transitorycomputer program product. Accordingly, aspects of the disclosure maytake the form of an entirely hardware embodiment, an entirely softwareembodiment (including firmware, resident software, micro-code, etc.) oran embodiment combining non-transitory software and hardware aspectsthat may all generally be referred to herein as a “circuit,” “module” or“system.” Furthermore, aspects of the disclosure may take the form of acomputer program product embodied in one or more computer readablemedium(s) having computer readable program code embodied thereon.

Any combination of one or more computer readable medium(s) may beutilized. The computer readable medium may be a non-transitory computerreadable signal medium or a computer readable storage medium. Anon-transitory computer readable storage medium may be, for example, butnot limited to, an electronic, magnetic, optical, electromagnetic, orsemiconductor system, apparatus, or device, or any suitable combinationof the foregoing. More specific examples (a non-exhaustive list) of thecomputer readable storage medium would include the following: anelectrical connection having one or more wires, a portable computerdiskette, a hard disk, a random access memory (RAM), a read-only memory(ROM), an erasable programmable read-only memory (EPROM or Flashmemory), an optical fiber, a portable compact disc read-only memory(CD-ROM), an optical storage device, a magnetic storage device, or anysuitable combination of the foregoing. In the context of this document,a non-transitory computer readable storage medium may be any tangiblemedium that can contain, or store a program for use by or in connectionwith an instruction execution system, apparatus, or device.

Program code embodied on a non-transitory computer readable medium maybe transmitted using any appropriate medium, including but not limitedto wireless, wireline, optical fiber cable, RF, etc., or any suitablecombination of the foregoing.

Non-transitory computer program code for carrying out operations foraspects of the disclosure may be written in any combination of one ormore programming languages, including an object oriented programminglanguage such as Java®, Smalltalk, C++ or the like and conventionalprocedural programming languages, such as the “C” programming languageor similar programming languages. The program code may execute entirelyon the user's computer, partly on the user's computer, as a stand-alonesoftware package, partly on the user's computer and partly on a remotecomputer or entirely on the remote computer or server. In the latterscenario, the remote computer may be connected to the user's computerthrough any type of network, including a local area network (LAN) or awide area network (WAN), or the connection may be made to an externalcomputer (for example, through the Internet using an Internet ServiceProvider).

Aspects of the disclosure are described below with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems) and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer program instructions. These computer program instructions maybe provided to a processor of a general purpose computer, specialpurpose computer, or other programmable data processing apparatus toproduce a machine, such that the instructions, which execute via theprocessor of the computer or other programmable data processingapparatus, create means for implementing the functions/acts specified inthe flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in anon-transitory computer readable medium that can direct a computer,other programmable data processing apparatus, or other devices tofunction in a particular manner, such that the instructions stored inthe computer readable medium produce an article of manufacture includinginstructions which implement the function/act specified in the flowchartand/or block diagram block or blocks.

The computer program instructions may also be loaded onto a computer,other programmable data processing apparatus, or other devices to causea series of operational steps to be performed on the computer, otherprogrammable apparatus or other devices to produce a computerimplemented process such that the instructions which execute on thecomputer or other programmable apparatus provide processes forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks.

For purposes of describing the embodiments disclosed herein, twoelements are considered to be coupled when one element is able to sendan electrical signal to another element. The electrical signal mayrepresent, for example but not limited to, data, operating commands,status information, or electrical power, or any combination of theseelectrical signals. A coupling may be implemented by wired or wirelessconnection means.

Those skilled in the art will appreciate that various adaptations andmodifications can be configured without departing from the scope andspirit of the embodiments described herein. Therefore, it is to beunderstood that, within the scope of the appended claims, theembodiments of the invention may be practiced other than as specificallydescribed herein.

What is claimed is:
 1. A method comprising: specifying more than oneparticipant in a conference; invoking the conference upon connecting oneor more participants to the conference; and allocating resources toconnect participants to the conference upon the conference beinginvoked.
 2. The method of claim 1, further comprising: receiving arequest to connect to the conference by one or more participants.
 3. Themethod of claim 2, further comprising: delaying one or more requests toconnect to the conference by one or more participants until theconference is invoked.
 4. The method of claim 1, wherein the conferenceis invoked upon receiving one or more requests to connect to theconference by one or more participants.
 5. The method of claim 1,further comprising: invoking the conference upon receiving a request toconnect to the conference from any participant.
 6. The method of claim1, further comprising: contacting participants to connect theparticipants to the conference upon the conference being invoked.
 7. Themethod of claim 2, further comprising: authenticating participants tothe conference upon receiving one or more requests by one or moreparticipants to connect to the conference.
 8. A system comprising: anetwork interface for sending and receiving one or more of video dataand audio data between two or more endpoints; one or more of a videodata source and an audio data source located at more than one endpoint;and a control unit for controlling one or more of the video data and theaudio data between endpoints, the control unit operable to executeinstructions to: specify more than one participant in a conference,wherein at least one participant is remotely located; invoke theconference upon receiving one or more requests to connect to theconference by one or more participants; allocate resources upon theconference being invoked; and connect participants to the conference. 9.The system of claim 8, wherein the control unit is further operable to:receive a request to connect to the conference from one or moreparticipants.
 10. The system of claim 9, wherein the control unit isfurther operable to: delay the requests of one or more participants toconnect to the conference until the conference is invoked.
 11. Thesystem of claim 8, wherein the control unit is further operable to:delay the requests of one or more participants to connect to theconference until the request to connect to the conference by achairperson is received.
 12. The system of claim 8, wherein the controlunit is further operable to: allocate resources upon the conferencebeing invoked to connect participants to the conference, the resourcesallocated depending upon at least a quantity of participants connectedto the conference.
 13. The system of claim 8, wherein the control unitis further operable to: authenticate participants to the conference uponreceiving one or more requests to connect to the conference by one ormore participants.
 14. The system of claim 13, wherein participants areauthenticated to the conference using one or more of passcodeauthentication and biometric authentication.
 15. A method comprising:specifying more than one participant in a conference, where at least oneparticipant is remotely located; designating at least one participant aschairperson; receiving requests to connect to the conference from one ormore participants; delaying one or more requests to connect to theconference by one or more participants until the conference is invoked;invoking the conference upon receiving a request to connect to theconference by the chairperson; and allocating resources for connectingparticipants to the conference, the resources allocated depending uponparticipants connected.
 16. The method of claim 15, further comprising:messaging dial-in participants to request the participants to connect tothe conference.
 17. The method of claim 15, further comprising:contacting dial-out participants to request the participants to connectto the conference.
 18. The method of claim 15, further comprising:contacting dial-in participants with at least one failed request toconnect to the conference to request the participants to connect to theconference.
 19. The method of claim 15, further comprising:authenticating participants to the conference upon receiving one or morerequests to connect to the conference by one or more participants,wherein participants are authenticated using one or more of passcodeauthentication and biometric authentication.
 20. A system, comprising: astorage device; and a processor coupled to the storage device, theprocessor adapted to execute instructions stored in the storage deviceto: specify more than one participant in a conference, where at leastone participant is located remotely; designate at least one participantas chairperson; receive a request to connect to the conference by morethan one participant; determine if the chairperson has requested toconnect to the conference; if the chairperson has requested to connectto the conference then, invoke the conference, allocate resources forthe conference, and connect participants to the conference; and if thechairperson has not requested to connect to the conference then, delaythe connection of participants to the conference; and return to the actof determining if the chairperson has requested to connect to theconference.
 21. The system of claim 20, wherein the processor is furtheradapted to: message requests to specified participants to connect to theconference via a network.
 22. The system of claim 21, wherein thenetwork comprises at least one of a telecommunication network and acomputer network.
 23. The system of claim 21, wherein participants aremessaged using one or more of unicast messaging, multicast messaging,and broadcast messaging.
 24. The system of claim 20, wherein theprocessor is further adapted to: authenticate participants to theconference, wherein participants are authenticated using one or more ofpasscode authentication and biometric authentication.
 25. Anon-transitory computer-readable medium comprising instructions to causeone or more processors to: specify more than one participant in aconference where at least one participant is located remotely; designateat least one participant as chairperson; receive a request to connect tothe conference by more than one participant; determine if thechairperson has requested to connect to the conference; delay connectingone or more participants to the conference until the request to connectto the conference from the chairperson is received; invoke theconference upon receiving the request to connect to the conference fromthe chairperson; message participants to request the participants toconnect to the conference via a network, wherein dial-in participantswith at least one failed request to connect to the conference anddial-out participants are messaged to request the participants toconnect to the conference; and allocate resources to connectparticipants to the conference upon the conference being invoked, theresources allocated depending upon participants to connect to theconference.
 26. The non-transitory computer-readable medium of claim 25,wherein participants are messaged using one or more of unicastmessaging, multicast messaging, and broadcast messaging.